SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
Go

Go static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your GO code

  • All rules 70
  • Vulnerability20
  • Bug7
  • Security Hotspot14
  • Code Smell29
 
Tags
    Impact
      Clean code attribute
        1. Multi-line comments should not be empty

           Code Smell
        2. Functions should not have identical implementations

           Code Smell
        3. Cognitive Complexity of functions should not be too high

           Code Smell
        4. Go parser failure

           Code Smell
        5. Boolean checks should not be inverted

           Code Smell
        6. Two branches in a conditional structure should not have exactly the same implementation

           Code Smell
        7. "switch" statements should not be nested

           Code Smell
        8. "switch" statements should not have too many "case" clauses

           Code Smell
        9. Track lack of copyright and license headers

           Code Smell
        10. Functions and methods should not have too many lines

           Code Smell
        11. Control flow statements "if", "for" and "switch" should not be nested too deeply

           Code Smell
        12. Octal values should not be used

           Code Smell
        13. "switch" statements should have "default" clauses

           Code Smell
        14. "if ... else if" constructs should end with "else" clauses

           Code Smell
        15. Statements should be on separate lines

           Code Smell
        16. String literals should not be duplicated

           Code Smell
        17. Functions should not be empty

           Code Smell
        18. Local variable and function parameter names should comply with a naming convention

           Code Smell
        19. "switch case" clauses should not have too many lines

           Code Smell
        20. Track uses of "TODO" tags

           Code Smell
        21. Track uses of "FIXME" tags

           Code Smell
        22. Boolean literals should not be redundant

           Code Smell
        23. Redundant pairs of parentheses should be removed

           Code Smell
        24. Nested blocks of code should not be left empty

           Code Smell
        25. Functions should not have too many parameters

           Code Smell
        26. Expressions should not be too complex

           Code Smell
        27. Files should not have too many lines of code

           Code Smell
        28. Lines should not be too long

           Code Smell
        29. Function names should comply with a naming convention

           Code Smell

        Multi-line comments should not be empty

        intentionality - clear
        maintainability
        Code Smell

          Why is this an issue?

          Empty comments, as shown in the example, hurt readability and might indicate an oversight.

          /*  */
          
          /*
          
           */
          

          Some meaningful text should be added to the comment, or the comment markers should be removed.

            Available In:
          • SonarQube IdeCatch issues on the fly,
            in your IDE
          • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
          • SonarQube Community BuildAnalyze code in your
            on-premise CI
            Available Since
            9.1
          • SonarQube ServerAnalyze code in your
            on-premise CI
            Developer Edition
            Available Since
            9.1

          © 2008-2025 SonarSource SA. All rights reserved.

          Privacy Policy | Cookie Policy | Terms of Use